IO

2023-03-22 10:42| 来源: 网络整理| 查看: 265

Thanks for the quick reply Eric! I'm far from in an expert in these areas. java_export works fine referencing java_library rules and it works as one would expect: transitive external dependencies are included in the pom.xml file and transitive internal dependencies are included in the jar. I agree, the documentation is pretty light! In fact, java_export produces a java_library rule. The docs here are better: https://docs-legacy.aspect.build/bazelbuild/rules_jvm_external/4.1/defs.html#java_export-deploy_env

With IO_GRPC_GRPC_JAVA_OVERRIDE_TARGETS removed, I added grpc dependencies directly to the artifacts property on my maven_install rule:

"com.google.protobuf:protobuf-java:3.21.9", "com.google.protobuf:protobuf-java-util:3.21.9", "io.grpc:grpc-protobuf:1.50.2", "io.grpc:grpc-api:1.50.2", "io.grpc:grpc-stub:1.50.2", "io.grpc:grpc-core:1.50.2", "io.grpc:grpc-protobuf:1.50.2", "io.grpc:grpc-netty-shaded:1.50.2",

This appears to work fine.

Can you elaborate a little on why IO_GRPC_GRPC_JAVA_OVERRIDE_TARGETS is necessary? I ask to make sure I'm not shooting myself in the foot by removing it! The protobuf repository provides PROTOBUF_MAVEN_ARTIFACTS without any overrides, fwiw.

【本文地址】

IO

IO

今日新闻

推荐新闻